-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UPSTREAM: 59506: fix watch on multiple reqs #18514
UPSTREAM: 59506: fix watch on multiple reqs #18514
Conversation
/retest |
1 similar comment
/retest |
81bb300
to
76b38bb
Compare
e0a6d6f
to
d2adfee
Compare
d2adfee
to
b02c1e6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
b02c1e6
to
170d39f
Compare
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: juanvallejo, soltysh The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. |
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1537789
oc get <resource> --watch
only supports watching a single resource kind at a time.This check fails if more than one resource
Info
is returned.When dealing with large quantities of a single resource kind, or an amount that exceeds the value of
--chunk-size
, more than one request is made to the server causing a resourceInfo
to be created for each of the requests, ultimately causing the above check to fail even though we are dealing with the same type of resource.This patch modifies that check to take into account the GVKs of all infos returned, and only fail if at least one differs.
cc @deads2k @jeremyeder